home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
iso
/
9660
/
rockrdge
/
rrg.09
/
api.nr
next >
Wrap
Text File
|
1992-08-19
|
4KB
|
112 lines
.sp
.H 1 "REQUIREMENTS FOR SYSTEMS"
.sp
The System Use Sharing Protocol specifies that certain information
shall be communicated between a user and an implementation.
.sp
An information processing system that conforms to this protocol shall
be the subject of a description which identifies the means by which
the user may supply such information, or may obtain it when it is
made available, as specified in this standard.
.sp
.H 2 "Requirements for an Originating System"
.sp
All originating systems which claim to implement the System Use Sharing
Protocol must comply with the protocol throughout each recorded System
Use Area.
.sp
The implementation shall be capable of recording a set of System
Use Fields in System Use Areas that are specified in this standard,
on a Volume Set in accordance with one of the interchange levels
specified in ISO 9660:1988.
.sp
The implementation shall allow the data preparer to supply the information
that is to be recorded in the System Use Area according to the
System Use Sharing Protocol and shall supply the information for a field
if the data preparer does not supply it.
.sp
.H 2 "Requirements for a Receiving System"
.sp
All receiving systems which claim to implement the System Use Sharing
Protocol must implement the "CE" System Use Field as defined in this
specification.
.sp
Any System Use Field which the receiving system does not recognize is
to be ignored and skipped.
.sp
The implementation shall be capable of reading a set of System
Use Fields in System Use Areas that are specified in this standard
from a Volume Set in accordance with one of the interchange levels
specified in ISO 9660:1988.
.sp
The implementation shall allow the user to supply information sufficient
to enable the implementation to locate the System Use Fields in System
Use Areas required by the user, and to locate the volumes on which
these are recorded.
.sp
The implementation shall make available to the user the information
that is recorded in each of the System Use Fields in each System
Use Area.
.sp
.H 2 "Requirements for an Application Programming Interface"
.sp
All receiving systems which claim to implement the System
Use Sharing Protocol must implement an Application Programming
Interface (API) to provide access to the information recorded in
the System Use Areas within a volume.
.sp
.bp
.sp
.sp
The API must provide a mechanism to verify the use of the
SUSP (by checking for the existence of a valid "SP" field) and
retrieve data recorded in the System Use Areas within a volume.
The mechanism must, at a minimum, be able to retrieve, for each
Directory Record:
.sp
.sp
.BL
.LI
a complete, individual System Use Field, including all
header information, selectable by Signature, field count
or both; and,
.LI
the contents of the Skip Area, BP 1 to LEN_SKP of the
System Use Area of the Directory Record.
.LE
.sp
.sp
Optionally, the API may also provide a mechanism to
retrieve, for each Directory Record:
.sp
.sp
.BL
.LI
a concatenated collection of all fields with a specific
Signature in recorded order; or,
.LI
a concatenated collection of all fields in recorded order.
.LE
.sp
.sp
The mechanism to retrieve such data must be able to
correctly and transparently interpret pertinent "CE" System Use
Fields to assure the complete retrieval of the requested data.
.sp
.H 2 "Coexistence with other Extensions and SUSP Registry"
.sp
Adherence to the System Use Sharing Protocol provides for the
mutual coexistence of different system-specific extensions
to ISO 9660:1988 by defining System Use Fields to be recorded
in System Use Areas.
.sp
A registry system will be established to
monitor and record existing and new System Use Field specifications and
distribute this information to individuals or organizations pursuing
the implementation of new and/or compatible system-specific extensions.
.sp
.H 2 "Implementation Suggestions"
.sp
For special cases, receiving systems are encouraged to provide a mechanism
to optionally disable the System Use Sharing Protocol in its entirety.